home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19981211-19990422 / 000039_news@newsmaster….columbia.edu _Wed Dec 23 11:44:11 1998.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA04171
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Wed, 23 Dec 1998 11:44:07 -0500 (EST)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA00357
  7.     for kermit.misc@watsun; Wed, 23 Dec 1998 11:44:07 -0500 (EST)
  8. Path: news.columbia.edu!newsfeed.nyu.edu!newsfeed.axxsys.net!peerfeed.ncal.verio.net!bug.rahul.net!samba.rahul.net!rahul.net!a2i!dold.a2i!dold
  9. From: dold@81.usenet.us.com
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: Winoldap giving me problems!!
  12. Date: 23 Dec 1998 16:27:43 GMT
  13. Organization: a2i network
  14. Lines: 17
  15. Message-ID: <75r5lv$l6j$1@samba.rahul.net>
  16. References: <75e0dj$kue$1@news.worldonline.nl> <75e0qd$71h$1@apakabar.cc.columbia.edu> <75ldph$sf8$1@news.worldonline.nl>
  17. Reply-To: dold@network.rahul.net
  18. NNTP-Posting-Host: waltz.rahul.net
  19. NNTP-Posting-User: dold
  20. X-Newsreader: TIN [version 1.2 PL2]
  21. X-Comment: Encoded From: line allows replies that preserve original subject
  22. Xref: news.columbia.edu comp.protocols.kermit.misc:9671
  23.  
  24. : Frank da Cruz heeft geschreven in bericht
  25. : >: General Protection Fault in Winoldap
  26.  
  27. I started getting this one day, after K95 1.1.17 had been installed for
  28. quite a while (making it an old app? ;-).
  29.  
  30. In looking at the "details" of the crash, I saw the name of the executable
  31. causing the crash that occurred any time I double-clicked on a Kermit
  32. Shortcut.  I didn't recognize the name, but a search on Microsoft.com
  33. showed that it was part of my video driver.
  34.  
  35. I reloaded my video driver, and the problem went away.
  36.  
  37. -- 
  38. ---
  39. Clarence A Dold - dold@network.rahul.net
  40.                 - Pope Valley & Napa CA.